Biometric Device Utilizing Finger Sequence for Authentication

ABSTRACT

A system and method for enhancing biometric security utilizing a fingerprint sequence authentication process. The method comprising, during an enrollment period for an electronic transaction system, obtaining a set of fingerprint templates associated with a registering user; storing the fingerprint templates on a memory of the electronic transaction system; determining an verification sequence unique to the registering user, wherein the verification sequence comprises a pattern of entering fingerprint images; and associating the verification sequence with the stored set of fingerprint templates to be used for a subsequent authentication of the registering user.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent application Ser. No. 14/603,703, filed Jan. 23, 2015; and is related to co-pending U.S. patent application Ser. No. 14/596,508, filed Jan. 14, 2015, entitled “System and Method for Requesting Reconciliation of Electronic Transaction Records for Enhanced Security”; U.S. patent application Ser. No. 14/596,472, filed Jan. 14, 2015, entitled “System and Method for Comparing Electronic Transaction Records for Enhanced Security”; U.S. patent application Ser. No. 14/596,420, filed Jan. 14, 2015, entitled “System and Method for Reconciling Electronic Transaction Records for Enhanced Security”; and U.S. patent application Ser. No. 14/596,572, filed Jan. 14, 2015, entitled “Smart Card Systems Comprising a Card and a Carrier,” which are all incorporated herein by reference in their entirety.

FIELD OF THE INVENTION

The present disclosure relates generally to biometric security, and more particularly, some embodiments relate to biometric authentication utilizing a fingerprint sequence.

BACKGROUND

Electronic transactions, such as credit card transactions, can be conducted using smart cards. A smart card is a device that includes an embedded integrated circuit chip that can be either a secure processing module (e.g., microprocessor, microcontroller, or equivalent intelligence) operating with an internal or external memory or a memory chip alone. Smart cards can provide identification, authentication, data storage, and application processing, as well as serving as credit or ATM debit cards, phone or fuel cards, and high-security access-control cards for granting access to a building or computer. Smart cards can authenticate the identity of a user by employing a public key infrastructure (PKI). This authentication process may be conducted in a variety of ways, including through the use of a pin, password, or biometric authentication, or a combination of methods for added layers of security.

BRIEF SUMMARY OF THE INVENTION

According to various embodiments of the disclosed technology, a method of enhanced biometric security is provided, comprising, during an enrollment period obtaining a set of fingerprint templates associated with a registering user; storing the fingerprint templates on a memory of the electronic transaction system; determining a verification sequence unique to the registering user, wherein the verification sequence comprises a pattern of entering fingerprint images; and associating the verification sequence with the stored set of fingerprint templates to be used for a subsequent authentication of the registering user.

According to various embodiments of the disclosed technology, a method of authenticating a registered user in an electronic transaction system is provided, comprising obtaining one or more fingerprint templates associated with a party requesting a new transaction, the one or more fingerprint templates associated with the party generated from one or more fingerprint images entered by the party in a first sequence; comparing the one or more fingerprint templates associated with the party to one or more fingerprint templates associated with a registered user and a second sequence, the set of fingerprint templates generated from a set of fingerprint images entered by the registered user during an enrollment process; and determining whether there is a match between the first sequence and the second sequence.

According to various embodiments of the disclosed technology, an electronic transactions system is provided, comprising a fingerprint scanner configured to obtain one or more fingerprint images entered by a party requesting a new transaction in a first sequence; a memory for storing a set of fingerprint templates associated with a registered user and a second sequence, the set of fingerprint templates generated from a plurality of fingerprint images entered by the registered user during an enrollment process; and one or more processing modules communicatively coupled to the memory and the fingerprint scanner, and configured to: generate one or more fingerprint templates associated with the party from the one or more fingerprint images entered by the party via the fingerprint scanner; compare the one or more fingerprint templates associated with the party to one or more fingerprint templates from the set of fingerprint templates associated with the registered user; and determine whether there is a match between the first sequence and the second sequence.

Other features and aspects of the disclosed technology will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, which illustrate, by way of example, the features in accordance with embodiments of the disclosed technology. The summary is not intended to limit the scope of any inventions described herein, which are defined solely by the claims attached hereto.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

The technology disclosed herein, in accordance with one or more various embodiments, is described in detail with reference to the following figures. The drawings are provided for purposes of illustration only and merely depict typical or example embodiments of the disclosed technology. These drawings are provided to facilitate the reader's understanding of the disclosed technology and shall not be considered limiting of the breadth, scope, or applicability thereof. It should be noted that for clarity and ease of illustration these drawings are not necessarily made to scale.

FIGS. 1A & 1B are example environments within which various embodiments of the technology disclosed herein may be implemented.

FIG. 2 is an example diagram of a personal transaction device that may be used in accordance with various embodiments of the technology disclosed herein.

FIG. 3 is an example diagram of a transaction using a personal transaction device in accordance with the technology disclosed herein.

FIG. 4 is an example flowchart of an authentication process in accordance with the technology disclosed herein.

FIG. 5 is another example diagram of a transaction using a personal transaction device in accordance with the technology disclosed herein.

FIG. 6 is an example flowchart of an enrollment process in accordance with the technology disclosed herein.

FIG. 7 is an example diagram of a computing module that may be used in implementing various features of embodiments of the technology disclosed herein.

The figures are not intended to be exhaustive or to limit the invention to the precise form disclosed. It should be understood that the invention can be practiced with modification and alteration, and that the disclosed technology be limited only by the claims and the equivalents thereof.

DETAILED DESCRIPTION

Embodiments of the technology disclosed herein are directed toward a system for and method of enhancing the security of a biometric device. More particularly, the various embodiments of the technology disclosed herein relate to biometric security utilizing fingerprint sequence authentication.

In the following detailed description, numerous specific details are set forth to provide a full understanding of various aspects of the subject disclosure. It will be apparent, however, to one ordinarily skilled in the art that various aspects of the subject disclosure may be practiced without some of these specific details. In other instances, well-known structures and techniques have not been shown in detail to avoid unnecessarily obscuring the subject disclosure.

Before describing the technology disclosed in detail, it is useful to describe an example environment within which the technology can be implemented. FIG. 1A is a block diagram of an example electronic transaction system 100 that can implement a finger sequence authentication procedure according to certain aspects of the present disclosure. The system 100 includes an electronic portable transaction device (PTD) 110, a transaction processing system (TPS) 130, and an interface device 120 that facilitates communications between the PTD 110 and the TPS 130. The PTD 110 can be, for example, a smart card, a smart key, a smart fob, or a mobile device. In some embodiments, the PTD 110 can include a biometric authentication module (not shown) for biometric authentication, as discussed in more detail with regards to FIG. 2.

The PTD 110 can conduct various types of electronic transactions with the TPS 130 via the interface device 120. For financial transaction applications, the PTD 110 can be a smart payment card such as a smart credit, debit, and/or prepaid card, or a smartphone with a payment transaction application. The TPS 130 can be a payment processing system of a merchant (e.g., Target®), a bank (e.g., Bank of America®), or a card issuer (e.g., Vise). The interface device 120 can be a point of sale (POS) terminal that can communicate with the PTD 110 using a contact method (e.g., matching male and female contact pads) or a contactless method (e.g., RFID, Bluetooth, NFC, Wi-Fi, ZigBee).

In some embodiments, the PTD 110 may communicate directly with the TPS 130 without an interface such as the interface device 120. For example, the PTD 110 can be equipped with a transceiver that can communicate with a cellular network such as a 3G UMTS or 4G LTE network. In some embodiments, the PTD 110 can be a smart phone capable of communicating with a cellular network.

For access control applications, the PTD 110 can be a smart access card, smart fob, or smart key for providing access to a facility or computer. For example, a PTD 110 in accordance with the present disclosure may be required to gain access to one or more of a secured facility, specific areas within a facility, a particular computing device or piece of equipment, a computer network, or a combination thereof. The TPS 130 can be a server in a central computer system, or a dedicated access controller that controls access to a facility or computer. Interface device 120 can be a card, fob, or key reader that can communicate with the PTD 110 using a contact method (e.g., contact pads) or a contactless method (e.g., RFID, Bluetooth, NFC, Wi-Fi, ZigBee).

In various embodiments, interface 120 may communicate with TPS 130 over network 140. Network 140 may be any communications network, such as a cellular or data network, a satellite network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a personal area network (PAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), or any combination thereof. Accordingly, network 140 may employ various communication media, such as a coaxial cable, fiber optic cable system, Ethernet, radio waves, etc.

In the illustrated example of FIG. 1A, the PTD 110 includes a processing module 112 and a data storage device 114; the interface device 120 includes a processing module 122 and a data storage device 124; and the TPS 130 includes a processing module 132 and a data storage device 134. In some embodiments, the PTD 110 can include a biometric authentication module (not shown) that includes a biometric sensor and a controller. The processing modules 112, 122, and 132, depending on the application, may be a microprocessor, microcontroller, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), computer, server, or any combination of components or devices configured to perform and/or control the functions of the PTD 110, interface device 120, and TPS 130, respectively. The data storage devices 114, 124, and 134, depending on the application, may be a read-only memory (ROM), such as EPROM or EEPROM, flash, a hard disk, a database, or any other storage component capable of storing executory programs and information for use by the processing modules 112, 122, and 132, respectively. Although PTD 110, interface device 120, and TPS 130 are all shown including a processing module (112, 122, 132) and a data storage device (114, 124, 134), such components are not required in all embodiments. In various embodiments, only one data storage device or only one processing module may be present that is accessible by one or more of the PTD, the interface device, and the TPS.

FIG. 1B illustrates another example electronic transaction system 150 that can implement a finger sequence authentication procedure according to certain aspects of the present disclosure. As illustrated in FIG. 1B, electronic transactions occur between a portable transaction device (PTD) 110B and a transaction processing system (TPS) 130B over network 140B, without an interface device. By way of example, a shopper may use a smartphone equipped with a camera to capture an image of a code (e.g., bar or QR code) to make a payment for a product or service by transmitting payment information to a card payment processing system via network 140B, in this case a cellular network. By way of another example, an access card reader at a facility may store information (e.g., passwords and/or security tokens) associated with employees authorized to enter the facility and, upon reading an access card, may compare security information received from the card with the stored information and grant or deny access depending on the outcome of the comparison.

There are many examples of biometric devices with which the present disclosure can be implemented. One example is the biometric smart card illustrated in FIG. 2. In various embodiments, card 200 has substantially the same shape and form factor as conventional credit and debit cards. Card 200 comprises a processing module 212 and a memory 214. Processing module 212 may be a microprocessor, microcontroller, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or any combination of components configured to perform and/or control the functions of card 200. Memory 214 may be a read-only memory (ROM) such as EPROM or EEPROM, flash, or any other storage component capable of storing executory programs and information for use by the processing module 212. Memory 214 can be internal to processor 212.

Card 200 includes a transaction interface 216. Transaction interface 216 is communicatively coupled to processing module 212. In various embodiments, transaction interface 216 is configured to communicate with TPS 130 through interface device 120 described above with respect to FIG. 1. Interface device 120 may be any point-of-sale (POS) or other transaction terminal connected to TPS 130 and configured to enable transactions with card 200 to occur.

In various embodiments, transaction interface 216 may include one or more conductive pads or pins that make electrical contact with corresponding conductive pads or pins provided in interface device 120. Data communication between card 200 and interface device 120 occurs through transaction interface 216. In various embodiments, when card 200 is engaged with interface device 120 for a transaction, some of the conductive pads of transaction interface 216 provide paths by which electrical power flows from interface device 120 to the components of card 200 via power line 218. This eliminates the need for card 200 to have its own on-board power source, simplifying design and manufacture.

In other embodiments, card 200 may include additional components to allow direct communication with TPS 130 without the need of interface device 120. Card 200 may include components required to allow contactless communication, such as RFID, Bluetooth, NFC, Wi-Fi, or ZigBee communication with TPS 130.

As shown in FIG. 2, card 200 further includes a biometric authentication module 220. In various embodiments, biometric authentication module 220 includes an authentication memory 224, a controller module 226, and a biometric sensor 222. Authentication memory 224 may be configured to store a template of the fingerprints of an authorized (e.g., registered) user for authentication purposes. In addition, authentication memory 224 may also be configured to store a copy of an authentication sequence. The authentication process is described in more detail below. Authentication memory 224 may be a read-only memory (ROM) such as EPROM or EEPROM, flash, or any other storage component capable of storing biometric data of one or more authorized users at the time card 200 is issued. In various embodiments, authentication memory 224 may be capable of both read and write commands to allow for the addition of other later authorized users through a reenrollment process after issuance of the card. In various embodiments, authentication memory 224 and memory 214 may be the same component.

Controller 226 is a processing module configured to execute authentication application programming stored in memory 224. In various embodiments, controller 226 may accept a fingerprint image input from sensor 222 and perform additional processing (e.g., extracting, focusing, aligning, rotating, scaling, normalizing and/or formatting) operations on the image to generate a fingerprint template that can be compared to a stored fingerprint template associated with an authorized (e.g., registered) user. In other embodiments, controller 226 can receive an already processed fingerprint template from sensor 222. Controller 226 is coupled to processing module 212 through connection 228. In various embodiments, controller 226 may be a separate hardware processing module from processing module 212. In various embodiments, controller 226 may be implemented in software, such as a virtual machine (VM) executed using processing module 212. In such an embodiment, additional security features may be implemented within processing module 212, such as partitioning between the VM and the card operating system to ensure that no unauthorized access to the controller module occurs. In various embodiments, the authentication application programming executed by controller 226 may be stored in memory 214 and accessible by controller 226 through processing module 212. In various embodiments, controller 226 may have direct access to memory 214.

Biometric sensor 222 is a biometric reader or scanner capable of reading or scanning a user's fingerprints. As discussed above, the biometric input from sensor 222 can be sent directly to controller 226 in order to allow controller 226 to perform formatting operations to generate a fingerprint template. In various embodiments, sensor 222 may be capable of formatting the fingerprint image prior to sending the fingerprint image to controller 226.

Other biometric devices with which the present disclosure may be implemented include smart fobs, smart keys, and mobile devices, among others. For ease of discussion, the authentication process and embodiments thereof are discussed with regards to the biometric-enabled smart card shown in FIG. 2. This discussion should not be read to limit the embodiments to only transactions involving smart cards, as the present disclosure is compatible with any biometric device.

To biometrically authenticate the identity of a person requesting a new transaction involving the biometric smart card 200, a processor in the card 200 can perform a comparison and a matching of one or more fingerprint templates associated with the person (the templates generated from fingerprint images received from biometric sensor 222) to one or more fingerprint templates associated with a registered user stored in a memory (e.g., memory 224 or memory 214). In some embodiments, the controller 226 performs both the generation of fingerprint templates associated with the person and the comparison and matching of the fingerprint templates to the stored fingerprint templates associated with the registered user. In other embodiments, the controller 226 performs the generation of fingerprint templates associated with the person and the processing module 212 performs the comparison and matching of the fingerprint templates to the stored fingerprint templates associated with the registered user.

In various embodiments, card 200 may have only a single component for processing both the transaction and authentication functions of card 200. In various embodiments, this single processing component may be processing module 212, and processing module 212 may be configured to execute both transaction applications and the functions of controller 226 described above. This eliminates the need for multiple processing units on the card and lowers the complexity of the design. In those embodiments employing a single processing component, the single processing component performs the generation of fingerprint templates associated with a person requesting a new transaction and the comparison and matching of the fingerprint templates to stored fingerprint templates associated with a registered user.

FIG. 3 illustrates an example transaction system 300 implementing card 200. In the illustrated example, the system 300 includes interface device 120 and TPS 130, described above with regards to FIG. 1. Also illustrated is card 200, which corresponds with the PTD 110 of FIG. 1. Although described in terms of card 200, the description should not be read to limit the present disclosure. In other embodiments, other PTDs may be used, such as a mobile device, a smart key, a smart fob, or a combination thereof. As illustrated in FIG. 3, interface device 120 includes a PTD interface 126, a processing module 122, and a data storage device 124. TPS 130 includes a processing module 132, and a data storage device 134, and a network interface 136 for communicating with interface device 120 via a communication network 140.

PTD interface 126 and transaction interface 216 on card 200 provide a communication link between card 200 and interface device 120. Using this communication link, card 200 can communicate authentication- and/or transaction-related data with interface device 120 and/or TPS 130. In various embodiments, interface device 120 may be a terminal and PTD interface 126 may be a physical card reader or scanner. In such embodiments, card 200 interacts with interface device 120 by inserting card 200 into the card reader, or scanning interface 216 of card 200 with the card scanner of interface device 120. In other embodiments, card 200 may include components necessary to enable contactless transactions, such as transceivers required for RFID, Bluetooth, NFC, or ZigBee communication. In various embodiments, interface device 120 supplies power to card 200 through this physical connection. In other embodiments, card 200 may include on on-board power source to supply power to the card components. In still other embodiments, card 200 may include wires or coils configured to receive power through induction principles, such as induction through NFC.

For ease of discussion, card 200 was used in descripting transaction system 300. This use, however, should not be read to limit the scope of the present disclosure. Transaction system 300 may be implemented in the same fashion using any PTD 110.

Authenticating the identity of a person attempting to conduct a transaction using a biometric-enabled device, such as card 200, is important. FIG. 4 is a flow diagram of an example authentication process 400 in accordance with the present disclosure. Although discussed in regards to the transaction environment illustrated in FIG. 3, implementation of authentication process 400 should not be limited to the transaction environment of FIG. 3. As one of ordinary skill in the art would recognize, authentication process 400 is applicable in any transaction environment in which fingerprint identification is implemented as a security layer, and with any biometric device. For ease of discussion, authentication process 400 is described in relation to a transaction occurring using a smart card containing a biometric authentication module. Where appropriate, different embodiments may be discussed.

At operation 402, one or more fingerprint templates associated with a party requesting a transaction are obtained. In various embodiments, the one or more fingerprint templates associated with the party are generated by processing (e.g., extracting, focusing, aligning, rotating, scaling, normalizing and/or formatting) fingerprint images entered by the party requesting the new transaction in a first sequence using a fingerprint scanner embedded on a smart card being used to conduct the transaction. In other embodiments, the fingerprint scanner may be part of a transaction terminal, such as interface device 120.

At operation 404, one or more fingerprint templates associated with a registered user authorized to use the smart card are obtained from a memory of the transaction system. In various embodiments, the one or more fingerprint templates associated with the registered user are obtained from a set of fingerprint templates generated from a set of fingerprint images entered by the registered user in a second sequence during an example enrollment process explained below with respect to FIG. 6. In various embodiments, the set of fingerprint templates is stored in authentication memory 224. In other embodiments, the set of fingerprint templates may be stored within data storage devices 134 or 124. In other embodiments, the set of fingerprint templates may be stored in one or more of the different memories discussed above to ensure access to the templates during a transaction.

At operation 406, the one or more fingerprint templates associated with the party requesting the transaction are compared with the one or more fingerprint templates associated with the registered user to authenticate the identity of the party. In various embodiments, the comparison can performed according to their respective sequences, meaning that the one or more fingerprint templates associated with the party in the first sequence are compared with the one or more fingerprint templates associated with the registered party in the second sequence.

At decision 408, a determination is made whether there is a match between the first sequence and the second sequence. In various embodiments, decision 408 may occur during operation 406. The criterion for a match may depend on the algorithm implemented by the operator of the transaction system. For example, the algorithm may involve determining whether a difference between compared fingerprint templates is within a predetermined threshold value (e.g., percentage). In some embodiments, a match/no-match decision is made right after a fingerprint image is received from the party requesting the transaction. In such an embodiment, the party may be rejected after a first fingerprint entry. In other embodiments, the party is allowed to enter the entire sequence of fingerprint images before the decision is made.

If a match is found, the party requesting the transaction is authenticated and the transaction is permitted to continue. In various embodiments, an indication of authentication may be presented to the party via a display on the PTD 110 used, such as smart card 200, or on a display included in the transaction terminal used, such as interface device 120. In other embodiments, a record of successful authentication may be recorded in one or more of authentication memory 224, data storage devices 124 and 134, or a combination thereof. In this way, an authenticated party may be able to conduct several transactions during a session without the need to go through the authentication process each time. In other embodiments, an indication of a successful authentication may be stored in volatile memory only, such as random access memory (RAM). In this way, multiple transactions may be conducted during a single session, but once power is removed the authentication is lost, requiring reauthentication to establish a new transaction session.

If no match is found, the party requesting the transaction is not authenticated and the transaction is not permitted to continue. In various embodiments, an indication of an unauthenticated request may be presented to the party through a display, in a similar fashion as described above with regards to a successful authentication. In other embodiments, an indication of an unauthenticated request may be sent to the TPS 130 to alert the operator that an unauthenticated transaction was attempted. Additional messages to the registered user may be sent, depending on any alert system implemented by the operator of the transaction system.

In various embodiments, the unauthenticated party may be requested to enter a new set of fingerprint images if no match is found. In this way, errors associated with a bad scan by the fingerprint scanner may be accounted for by allowing a second chance to obtain the one or more fingerprint templates, as discussed with regards to operation 402. In various embodiments, the unauthenticated party may only reenter a new set of fingerprint images once before the transaction is terminated and no transaction is permitted. In other embodiments, if no match is found after a predetermined number of tries, the transaction is terminated and the unauthenticated party is locked out of conducting transactions and/or the electronic portable transaction device may be disabled. In such a way, an additional layer of security may be included within the system.

Although discussed in regards to transactions involving a smart card and an interface device, the authentication process of the present disclosure is applicable in other transaction environments. In various embodiments, card 200 may be any of the other devices associated with PTD 110 described in regard to FIG. 1, such as a smart key, a smart fob, or a mobile device, among others. In various embodiments, a combination of different biometric devices may be used to function as PTD 110. In various embodiments, PTD 110B may be able to communicate and conduct transactions with TPS 130B without interface device 120, as illustrated in FIG. 1B. In various embodiments, PTD 110B may include a smart card, similar to card 200, without contactless communication capability, and a card carrier designed to enable card 200 to conduct contactless communication with TPS 130B, such as the smart card system disclosed in “Smart Card Systems Comprising a Card and a Carrier,” which is incorporated herein by reference.

In various embodiments, the authentication process illustrated in FIG. 4 may be performed by more than one entity. For example, take transaction system 150 illustrated in FIG. 1B. In various embodiments, PTD 110B may be a smartphone equipped with a fingerprint scanner in communication with TPS 130B over network 140B. The smartphone may be configured to perform operation 402 of FIG. 4, querying the user to enter fingerprint images in a first sequence using the fingerprint scanner and generating the fingerprint templates. The smartphone can then transmit those fingerprint images or fingerprint templates to TPS 130B for back-end performance of operations 404-412. In other embodiments, the smartphone may only obtain the fingerprint images entered by the user in a first sequence and transmit those fingerprint images for generation of fingerprint templates by TPS 130B, in accordance with the description above regarding FIG. 4. In various embodiments involving the transaction system 100 of FIG. 1A, the operations of FIG. 4 may be performed by one or more of TPS 130, PTD, 110, interface device 120, or any combination thereof.

Although shown in FIGS. 2 and 3 as being part of card 200, one or more components of the biometric authentication module 220 may be included within other devices within the system. As shown in FIG. 5, interface device 520 may include the same components as interface device 120, in addition to a biometric scanner 522 (e.g., a fingerprint scanner). Interface device 520 may be implemented with card 200, or with other smart card embodiments that do not include the biometric authentication module 220 of card 200. In the illustrated embodiment of FIG. 5, the biometric scanning functions described above in regards to the biometric authentication module 220 are performed by biometric scanner 522 in interface device 520. In various embodiments, biometric sensor 222 on card 200 may still be able to communicate with controlled 226, allowing an unauthenticated user to input fingerprint images in accordance with the example process of FIG. 4 using either scanner. In other embodiments, interface device 520 may communicate with processing module 212 and request that biometric sensor 222 be deactivated while the transaction is occurring. In other embodiments, biometric sensor 222 may not be included in card 200.

The authentication process would proceed in the same way as discussed above in regard to FIG. 4, except that the fingerprint images used to generate the one or more fingerprint templates associated with a person requesting a transaction would be inputted through sensor 522 of interface device 520 and transmitted to card 200 through interface 521 for authentication processing. In other embodiments, interface device 520 may conduct the authentication processing as well. In such embodiments, processing module 524 may perform the functions of controller 226. In other embodiments, data storage device 526 may be configured to act like authentication memory 224, storing the set of fingerprint templates associated with a registered user in the second sequence as discussed above with regards to operation 404. In some embodiments, all the components of biometric authentication module 220 may be included in interface device 520, and card 200 may not include a biometric authentication module.

As discussed above, the authentication process includes a set of fingerprint templates associated with a registered user in a second sequence stored on a memory of the transaction system. This set of fingerprint templates is obtained and identified during an enrollment process. A registered user's fingerprint templates and a verification sequence are created during the period. The implementation of an enrollment period depends on the operator of the transaction system, such as the bank managing the user's account. The operator may have a single enrollment period at the time a biometric device, like PTD 110 and card 200, is enrolled in the system. In various embodiments, an operator may allow a registered user to enroll a new or additional user after the biometric device has already been enrolled.

An example enrollment process is described in reference to FIG. 6. This is only an example enrollment process, and should not be read to limit the present disclosure.

At operation 602, a set of fingerprint templates associated with a registering user are obtained. The fingerprint templates can be generated from a set of fingerprint images of the registering user by processing (e.g., extracting, focusing, aligning, rotating, scaling, normalizing and/or formatting) the fingerprint images. The set of fingerprint images can be obtained using a fingerprint scanner. In various embodiments, the enrollment process may be directed at enrolling a smart card, smart key, smart fob, a mobile device, or a combination thereof with the transaction system. In various embodiments, the fingerprint scanner used to obtain the fingerprint templates may be a fingerprint scanner embedded on the smart card, smart key, or smart fob. In some embodiments, the fingerprint scanner may be included in a mobile device (e.g., smart phone, PDA, tablet, laptop, portable POS terminal) used for conducting transaction, both with or without an interface device like interface device 120. The fingerprint scanner within the mobile device may be a physical component, such as an image scanner or touch sensitive pad, or could be an application utilizing other components of the mobile device, such as an application that scans fingerprint images using a touch screen of the mobile device or through a camera included in the mobile device. In other embodiments, the fingerprint scanner used could be a fingerprint scanner included within a transaction terminal connected to the transaction system. In other embodiments, the fingerprint templates may be obtained via a standalone fingerprint scanner connected to the transaction system at a transaction system's operator's enrollment location, such as a bank branch.

In various embodiments, the set of fingerprint templates obtained may include only a subset of fingerprint templates associated with the registering user. For example, the set of fingerprint templates may include templates for only the registering user's ring, middle, and index fingers on the left hand, and only the thumb and index finger on the right hand. In other embodiments, a different grouping of fingers between the registering user's two hands may be used. In various embodiments, the set of fingerprint templates may be limited to a threshold amount of templates. In various embodiments, the set of fingerprint templates may be limited to the fingerprints of a single hand.

In various embodiments, the set of fingerprint templates may be obtained during an enrollment period. The enrollment period may be the initial period in which a user or user's account is registered with the transaction system. In various embodiments, the enrollment period may occur only once, prior to the user being able to conduct any transactions. In other embodiments, the registering user may be able to re-enroll at a later time, such as when a new authorized user must be added to the account or a new biometric device is to be registered. In various embodiments, the fingerprint templates may be obtained prior to the enrollment process. For example, the registering user may provide fingerprint templates prior to the date of enrollment for processing purposes, or the fingerprint templates may be obtained from another stored set of fingerprint templates associated with the registering user.

At operation 604, the set of fingerprint templates are stored on a memory of the transaction system. Storage of the fingerprint templates allows retrieval of the fingerprint templates for authentication purposes prior to completing a transaction, such as for use in the authentication process discussed above. The memory of the transaction system may be any compatible data storage component, such as a read-only memory (ROM), such as EPROM or EEPROM, flash, a hard disk, a database, or any other storage component capable of storing executory programs and information. In various embodiments, the set of fingerprint templates may be stored on a memory of a smart card or mobile device. In other embodiments, the set of fingerprint templates may be stored on a memory of a transaction terminal, such as a POS terminal. In other embodiments, the set of fingerprint templates may be stored on a data storage device of the transaction system, such as a central database. In various embodiments, the set of fingerprint templates may be stored in more than one location to ensure that the templates may be retrieved for authentication purposes.

At operation 606, a verification sequence is determined that is unique to the registering user. The verification sequence comprises a pattern of entry of a registering user's fingerprints, similar to a personal identification number (PIN) or passcode. Instead of entering a numerical code, an unauthenticated user must provide fingerprint images in an ordered pattern dictated by the verification sequence. For example, if the verification sequence unique to the individual is “ring finger, thumb, index finger,” the unauthenticated user must first provide an image of his or her ring finger, then the thumb, then the index finger. If not entered correctly, the authentication process fails. The example sequence used was simplified for explanatory purposes and should not be read to limit the embodiments of the present disclosure.

In various embodiments, the verification sequence may be determined based on the ordered sequence in which the fingerprint templates were obtained. In other embodiments, the verification sequence may be chosen by the registering user (e.g., from a list of fingerprint images or fingers to the user) before or after the set of fingerprint templates are obtained. In other embodiments, the verification sequence may be provided or suggested by the operator of the transaction system. In various embodiments, the verification sequence may be stored on a memory of the transaction system in the same way as the set of fingerprint templates discussed above with regards to operation 604.

At operation 608, the verification sequence is associated with the set of fingerprint templates associated with the registering user. In various embodiments, the verification sequence may be formatted as numerical values, such as the first entry is “one”, the second “two”, etc. For example, taking the simplified verification sequence discussed above, the registering user's ring finger template would be “one,” the thumb would be “two,” and the index finger “three.” Accordingly, when an unauthenticated user enters a fingerprint sequence, the corresponding templates can be retrieved based on the image to which it is compared: the first entered fingerprint is compared against template “one,” the second entered fingerprint against template “two,” etc. In other embodiments, the verification sequence may be associated with the fingerprint templates by ordering the fingerprint templates based on the verification sequence. In various embodiments, the verification sequence may be associated with corresponding fingerprint templates, such as the two fingerprint templates associated with a registering user's ring fingers (one for each hand). The associated verification sequence represents the second sequence associated with a registered user referenced above in regards to operation 404 of FIG. 4.

Although the example verification sequence discussed above speaks simply of images of a particular finger, the sequence may include additional identifiers. In various embodiments, the verification sequence may refer to the specific hand associated with the specific fingerprint template.

Although described as an enrollment process, the process of FIG. 6 may be used outside of the initial enrollment process to allow a registering user greater control over the account. In various embodiments, the process may be used to allow a registering user to change an already registered verification sequence. In such embodiments, one or more of the operations may be omitted, such as obtaining the set of fingerprint templates.

As used herein, the term set may refer to any collection of elements, whether finite or infinite. The term subset may refer to any collection of elements, wherein the elements are taken from a parent set; a subset may be the entire parent set. The term proper subset refers to a subset containing fewer elements than the parent set. The term sequence may refer to an ordered set or subset. The terms less than, less than or equal to, greater than, and greater than or equal to, may be used herein to describe the relations between various objects or members of ordered sets or sequences; these terms will be understood to refer to any appropriate ordering relation applicable to the objects being ordered.

As used herein, the term module might describe a given unit of functionality that can be performed in accordance with one or more embodiments of the technology disclosed herein. As used herein, a module might be implemented utilizing any form of hardware, software, or a combination thereof. For example, one or more processors, controllers, ASICs, PLAs, PALs, CPLDs, FPGAs, logical components, software routines or other mechanisms might be implemented to make up a module. In implementation, the various modules described herein might be implemented as discrete modules or the functions and features described can be shared in part or in total among one or more modules. In other words, as would be apparent to one of ordinary skill in the art after reading this description, the various features and functionality described herein may be implemented in any given application and can be implemented in one or more separate or shared modules in various combinations and permutations. Even though various features or elements of functionality may be individually described or claimed as separate modules, one of ordinary skill in the art will understand that these features and functionality can be shared among one or more common software and hardware elements, and such description shall not require or imply that separate hardware or software components are used to implement such features or functionality.

Where components or modules of the technology are implemented in whole or in part using software, in one embodiment, these software elements can be implemented to operate with a computing or processing module capable of carrying out the functionality described with respect thereto. One such example computing module is shown in FIG. 7. Various embodiments are described in terms of this example-computing module 700. After reading this description, it will become apparent to a person skilled in the relevant art how to implement the technology using other computing modules or architectures.

Referring now to FIG. 7, computing module 700 may represent, for example, computing or processing capabilities found within desktop, laptop and notebook computers; hand-held computing devices (PDA's, smart phones, cell phones, palmtops, etc.); mainframes, supercomputers, workstations or servers; or any other type of special-purpose or general-purpose computing devices as may be desirable or appropriate for a given application or environment. Computing module 700 might also represent computing capabilities embedded within or otherwise available to a given device. For example, a computing module might be found in other electronic devices such as, for example, digital cameras, navigation systems, cellular telephones, portable computing devices, modems, routers, WAPs, terminals and other electronic devices that might include some form of processing capability.

Computing module 700 might include, for example, one or more processors, controllers, control modules, or other processing devices, such as a processor 704. Processor 704 might be implemented using a general-purpose or special-purpose processing engine such as, for example, a microprocessor, controller, or other control logic. In the illustrated example, processor 704 is connected to a bus 702, although any communication medium can be used to facilitate interaction with other components of computing module 700 or to communicate externally.

Computing module 700 might also include one or more memory modules, simply referred to herein as main memory 706. For example, preferably random access memory (RAM) or other dynamic memory, might be used for storing information and instructions to be executed by processor 704. Main memory 706 might also be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 704. Computing module 700 might likewise include a read only memory (“ROM”) or other static storage device coupled to bus 702 for storing static information and instructions for processor 704.

The computing module 700 might also include one or more various forms of information storage mechanism 708, which might include, for example, a media drive 710 and a storage unit interface 714. The media drive 710 might include a drive or other mechanism to support fixed or removable storage media 712. For example, a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a CD or DVD drive (R or RW), or other removable or fixed media drive might be provided. Accordingly, storage media 712 might include, for example, a hard disk, a floppy disk, magnetic tape, cartridge, optical disk, a CD or DVD, or other fixed or removable medium that is read by, written to or accessed by media drive 710. As these examples illustrate, the storage media 712 can include a computer usable storage medium having stored therein computer software or data.

In alternative embodiments, information storage mechanism 708 might include other similar instrumentalities for allowing computer programs or other instructions or data to be loaded into computing module 700. Such instrumentalities might include, for example, a fixed or removable storage unit 716 and an interface 714. Examples of such storage units 716 and interfaces 714 can include a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, a PCMCIA slot and card, and other fixed or removable storage units 716 and interfaces 714 that allow software and data to be transferred from the storage unit 716 to computing module 700.

Computing module 700 might also include a communications interface 720. Communications interface 720 might be used to allow software and data to be transferred between computing module 700 and external devices. Examples of communications interface 720 might include a modem or softmodem, a network interface (such as an Ethernet, network interface card, WiMedia, IEEE 802.XX or other interface), a communications port (such as for example, a USB port, IR port, RS232 port Bluetooth® interface, or other port), or other communications interface. Software and data transferred via communications interface 720 might typically be carried on signals, which can be electronic, electromagnetic (which includes optical) or other signals capable of being exchanged by a given communications interface 720. These signals might be provided to communications interface 720 via a channel 722. This channel 722 might carry signals and might be implemented using a wired or wireless communication medium. Some examples of a channel might include a phone line, a cellular link, an RF link, an optical link, a network interface, a local or wide area network, and other wired or wireless communications channels.

In this document, the terms “computer program medium” and “computer usable medium” are used to generally refer to media such as, for example, memory 706, storage unit 716, media 712, and channel 722. These and other various forms of computer program media or computer usable media may be involved in carrying one or more sequences of one or more instructions to a processing device for execution. Such instructions embodied on the medium, are generally referred to as “computer program code” or a “computer program product” (which may be grouped in the form of computer programs or other groupings). When executed, such instructions might enable the computing module 700 to perform features or functions of the disclosed technology as discussed herein.

While various embodiments of the disclosed technology have been described above, it should be understood that they have been presented by way of example only, and not of limitation. Likewise, the various diagrams may depict an example architectural or other configuration for the disclosed technology, which is done to aid in understanding the features and functionality that can be included in the disclosed technology. The disclosed technology is not restricted to the illustrated example architectures or configurations, but the desired features can be implemented using a variety of alternative architectures and configurations. Indeed, it will be apparent to one of skill in the art how alternative functional, logical or physical partitioning and configurations can be implemented to implement the desired features of the technology disclosed herein. Also, a multitude of different constituent module names other than those depicted herein can be applied to the various partitions. Additionally, with regard to flow diagrams, operational descriptions and method claims, the order in which the steps are presented herein shall not mandate that various embodiments be implemented to perform the recited functionality in the same order unless the context dictates otherwise.

Although the disclosed technology is described above in terms of various exemplary embodiments and implementations, it should be understood that the various features, aspects and functionality described in one or more of the individual embodiments are not limited in their applicability to the particular embodiment with which they are described, but instead can be applied, alone or in various combinations, to one or more of the other embodiments of the disclosed technology, whether or not such embodiments are described and whether or not such features are presented as being a part of a described embodiment. Thus, the breadth and scope of the technology disclosed herein should not be limited by any of the above-described exemplary embodiments.

Terms and phrases used in this document, and variations thereof, unless otherwise expressly stated, should be construed as open ended as opposed to limiting. As examples of the foregoing: the term “including” should be read as meaning “including, without limitation” or the like; the term “example” is used to provide exemplary instances of the item in discussion, not an exhaustive or limiting list thereof; the terms “a” or “an” should be read as meaning “at least one,” “one or more” or the like; and adjectives such as “conventional,” “traditional,” “normal,” “standard,” “known” and terms of similar meaning should not be construed as limiting the item described to a given time period or to an item available as of a given time, but instead should be read to encompass conventional, traditional, normal, or standard technologies that may be available or known now or at any time in the future. Likewise, where this document refers to technologies that would be apparent or known to one of ordinary skill in the art, such technologies encompass those apparent or known to the skilled artisan now or at any time in the future.

The presence of broadening words and phrases such as “one or more,” “at least,” “but not limited to” or other like phrases in some instances shall not be read to mean that the narrower case is intended or required in instances where such broadening phrases may be absent. The use of the term “module” does not imply that the components or functionality described or claimed as part of the module are all configured in a common package. Indeed, any or all of the various components of a module, whether control logic or other components, can be combined in a single package or separately maintained and can further be distributed in multiple groupings or packages or across multiple locations.

Additionally, the various embodiments set forth herein are described in terms of exemplary block diagrams, flow charts and other illustrations. As will become apparent to one of ordinary skill in the art after reading this document, the illustrated embodiments and their various alternatives can be implemented without confinement to the illustrated examples. For example, block diagrams and their accompanying description should not be construed as mandating a particular architecture or configuration. 

We claim:
 1. A method of enhancing biometric security, comprising; during an enrollment period for an electronic transaction system, obtaining a set of fingerprint templates associated with a registering user; storing the fingerprint templates on a memory of the electronic transaction system; determining an verification sequence unique to the registering user, wherein the verification sequence comprises a pattern of entering fingerprint images; and associating the verification sequence with the stored set of fingerprint templates to be used for a subsequent authentication of the registering user.
 2. The method of claim 1, wherein the set of fingerprint templates are generated from a plurality of fingerprint images entered by the registering user via a fingerprint scanner.
 3. The method of claim 2, wherein the plurality of fingerprint images were entered by the registering user during the enrollment period.
 4. The method of claim 2, wherein the plurality of fingerprint images were entered by the registering user prior to the enrollment period.
 5. The method of claim 2, wherein the verification sequence is determined based on an order in which the plurality of fingerprint images were entered by the registering user.
 6. The method of claim 1, wherein the verification sequence is determined after the plurality of fingerprint images were obtained during the enrollment period.
 7. The method of claim 1, wherein the verification sequence is specified by the registering user.
 8. The method of claim 1, wherein the verification sequence is specified by the electronic transaction system.
 9. The method of claim 2, wherein the fingerprint scanner used to obtain the plurality of fingerprint images is embedded on a smart card, and the set of fingerprint templates is stored in a memory of the smart card.
 10. The method of claim 9 further comprising storing the verification sequence in the memory of the smart card.
 11. The method of claim 2, wherein the fingerprint scanner used to obtain the plurality of fingerprint images is included in a terminal connected to the transaction system.
 12. The method of claim 11, wherein the memory of the transaction system comprises a memory of the terminal connected to the transaction system.
 13. A method of authenticating a registered user in an electronic transaction system, comprising: obtaining one or more fingerprint templates associated with a party requesting a new transaction, the one or more fingerprint templates associated with the party generated from one or more fingerprint images entered by the party in a first sequence; comparing the one or more fingerprint templates associated with the party to one or more fingerprint templates associated with a registered user and a second sequence, the set of fingerprint templates generated from a set of fingerprint images entered by the registered user during an enrollment process; and determining whether there is a match between the first sequence and the second sequence.
 14. The method of claim 13, wherein the party requests the new transaction using a smart card comprising one or more processing modules and a memory, and the smart card is in communication with the electronic transaction system through a terminal connected to the electronic transaction system.
 15. The method of claim 14, wherein the fingerprint scanner is embedded on the smart card.
 16. The method of claim 15, wherein the one or more fingerprint templates associated with a registered user is stored on the memory of the smart card.
 17. The method of claim 16, wherein the determining step is performed at the terminal.
 18. The method of claim 14, wherein the fingerprint scanner is part of the terminal.
 19. The method of claim 18, wherein the determining step is performed at the smart card, and the one or more fingerprint images entered by the party in a first sequence are entered via the fingerprint scanner at the terminal.
 20. The method of claim 18, wherein the determining step is performed at the terminal, and the method further comprising accessing the memory on the smart card and retrieving the one or more fingerprint templates associated with a registered user. 